S3Drive - Media backup on Android

Hi @yz, I've created this item to carry on our conversation: https://discord.com/channels/1069654792902815845/1069654792902815848/1219004374421078118 so we have it, in one place. Regarding:

forced it via start backup. Tbh I haven't seen it automatically resuming the backup just yet.

There are triggers like app resume, app start (if "Backup when app starts" setting is on) and when new photo is taken (if "Background backup" setting is on). There isn't "retry the whole process" if at least one photo upload failed or some periodic scheduling just yet (e.g. restart process every 15 minutes) Finally, as I've stated here that app shouldn't mark failed media upload as success: https://discord.com/channels/1069654792902815845/1069654792902815848/1218969100735480018 It does seem there is a regression in that area. At the moment even if there is a failure it does increase the upload counter and the only way to reupload such media would be to use Reset / Match feature, until we have it fixed in a next release. In the meantime if you have any other questions or feedback regarding media backup (or anything else), don't hesitate to reach out. (edited)

Cheers! Cool, good to know! I'll keep you updated. And thanks for being so responsive (on a Sunday)

Yesterday I ran twice into the OOM issue again - which means that all files from a certain point onwards OOM. What I find slightly unusual is that I expect it to recover once the app is in the foreground again. It does not. But tbh Android's memory management is a mystery to me. Also, do you know why it OOMs - I would expect S3drive to stream the data and basically use a constant amount of memory.

7:26 AM

And it's currently stuck:

7:26 AM

7:27 AM

It's been like this since yesterday.

7:27 AM

These are the logs:

7:28 AM

7:31 AM

After force killing it, the app resumes:

7:31 AM

7:35 AM

This was 1.7.17

7:35 AM

I just updated it

7:36 AM

And it actually auto resumed after I opened the app

7:40 AM

That was the first time i saw that

7:41 AM

One thing around the upload speed - I am not sure why it's so low: (edited)

7:42 AM

I have a gigabit connection and I wouldn't expect backblaze to throttle

Another thing i just noticed: I see that the stats on the media backup page move forward (rather quickly), but the transfers page is empty (like 0 all around).

Just had an OOM condition again - what I found interesting is that the app felt very, very sluggish at that point. Which might point to a real memory leak? But I'm just speculating

Thank you for your comments, description and screenshots. It sounds like we need to trace down the OOM issues. I assume you use Backblaze, configured via S3 (not Rclone) screen on S3Drive? Do you use the 1.8.0 version already? (It contains couple improvements and fixes, especially related to error handling and marking assets as uploaded or not). We'll try to narrow down couple scenarios where OOM happens. In the meantime if you have any additional findings / thoughts please send them over. Sorry for these issues and thanks for your efforts helping us to improve the app !

Tom changed the channel name: Media backup on Android - OOM issues 3/21/2024 6:55 AM

I was wondering if this issue is still present on your end? We've just released 1.9.2 and it contains couple related improvements.